Conversation
… addresses issue 1028
| } | ||
| }, | ||
| "urls": { | ||
| "direct_download": "https://mvgo.org/data/gtfs.zip", |
There was a problem hiding this comment.
Create new feed and redirect
| } | ||
| }, | ||
| "urls": { | ||
| "direct_download": "https://s3.amazonaws.com/datatools-511ny/public/Watertown_Citibus.zip", |
There was a problem hiding this comment.
Create new feed and redirect
There was a problem hiding this comment.
Double check the feeds to see if they are same or different
There was a problem hiding this comment.
There was a problem hiding this comment.
In that case, you can remove the redirect and deprecation and just add 2881 as a new feed
There was a problem hiding this comment.
Sorry I mean to say that it is an updated feed (with a different URL). This would mean we need to deprecate the old feed (mdb-871) and add a redirect to the new feed (mdb-2881) right?
There was a problem hiding this comment.
The service date ranges are different but both active and the entities are slightly different. (I think the passio feed is the one they're using to match with realtime data, based on the fact that there are block entities and it's created by passio). I'd keep both.
There was a problem hiding this comment.
Ah right ok I see, I didn't think of this case. That's useful to know!
| } | ||
| }, | ||
| "urls": { | ||
| "direct_download": "http://data.trilliumtransit.com/gtfs/ruralcommunity-vt-us/ruralcommunity-vt-us.zip", |
There was a problem hiding this comment.
Create new feed because its flex feed
There was a problem hiding this comment.
Both URLs are actually flex feeds, so will create a new feed and redirect+deprecate the old one.
https://gtfs-validator-results.mobilitydata.org/b7f24148-791b-4686-88c1-56033083ed0c/report.html
https://gtfs-validator-results.mobilitydata.org/8a723c58-ee4c-442b-bfe8-b13a6ffc64bc/report.html
There was a problem hiding this comment.
The first report doesn't have any flex features (continuous stops doesn't count as GTFS-Flex...sorry, i should've shared that context)
There was a problem hiding this comment.
These are 2 separate feeds
There was a problem hiding this comment.
Ok I see, I think I'll read up more on flex to understand better 😅 I was just going off of booking_rules.txt. I checked if that was present but turns out it was empty in the non-flex feed anyways
…ddresses issue 1029
…t mdb-871; addresses issue 1028
…resses issue 1058
… stable id (mdb-2883); addresses issue 1030
…dresses issue 1022
…-2885); addresses issue 1008
…addresses issue 1028
…1029 New URL is in active feed mdb-2880
| "latest": "https://storage.googleapis.com/storage/v1/b/mdb-latest/o/us-new-york-watertown-citibus-gtfs-2881.zip?alt=media" | ||
| }, | ||
| "redirect": [ | ||
| { |
There was a problem hiding this comment.
redirect should be on 871, not on this feed
| "municipality": "Vancouver" | ||
| }, | ||
| "urls": { | ||
| "direct_download": "https://www.c-tran.com/images/Google/GoogleTransitUpload.zip", |
There was a problem hiding this comment.
This feed is already in the database: https://mobilitydatabase.org/feeds/gtfs/mdb-258 just need to change the http settings
emmambd
left a comment
There was a problem hiding this comment.
Added some comments - there's still some feeds that need to be modified
| "authentication_type": 0, | ||
| "license": "https://opendatacommons.org/licenses/by/summary/" | ||
| }, | ||
| "feed_contact_email": "nfo@mvcommunityshuttle.com", |
There was a problem hiding this comment.
Looks like this should be "info" rather than "nfo" for feed contact email
…e 1030 referred to https://mvcommunityshuttle.com/ for contact email
Addresses issues:
#1030 Add Mountain View Community Shuttle schedule feed
#1022 Add VTrans schedule feed
#1008 Add C-TRAN schedule feed
#1029 Update MVgo schedule feed with new direct download URL
#1058 Update RCT schedule feed with new direct download URL
#1028 Update Watertown Citibus schedule feed with new direct download URL
#1041 Update Centro schedule feed with new direct download URL
Note: Latest mdb stable id is mdb-2884